Custom Welcome Message Feature

This update introduces a customizable welcome message for the chat interface. Administrators can now configure a greeting directly through the librechat.yaml file, enhancing branding and overall user experience.

Closes: #2967
Docs: LibreChat-AI/librechat.ai#236

Key Changes

• Configuration & Setup:

  • Updated librechat.example.yaml to include a new customWelcome field, allowing administrators to define a custom greeting.

• Backend Enhancements:

  • Modified api/server/routes/config.js to read the customWelcome from librechat.yaml and include it in the startup configuration payload.
  • Updated the configuration schema in packages/data-provider/src/config.ts to optionally accept a customWelcome.

• Frontend Updates:

  • Refactored the welcome message logic in client/src/components/Chat/Landing.tsx to display the custom message when provided in the startup configuration.
  • Improved code readability and logic for handling both assistant and agent welcome messages.

Motivation and Context

By moving configuration to librechat.yaml, this change allows platform administrators to easily tailor the user experience with a custom greeting. The feature not only enhances first impressions but also contributes to a more personalized experience for end users.

Testing Process

1. Backend Testing:

   • Start the server with a librechat.yaml file that defines a custom welcome message.
   • Verify that a request to /api/config includes the customWelcome field in its response.

2. Frontend Testing:

   • Load the chat interface to confirm that the welcome message displays as configured.
   • Validate fallback behavior by testing scenarios where the custom welcome message is absent or empty.
   • Ensure that the logic for both assistant and agent welcome messages functions as expected.

Checklist

• My code adheres to this project's style guidelines.
• I have performed a self-review of my own code.
• I have commented in any complex areas of my code.
• My changes do not introduce new warnings.
• I have written tests demonstrating that my changes are effective.
• Local unit tests pass with my changes.
• Any dependent changes have been merged and published in downstream modules.
• A pull request for updating the documentation has been submitted.